Skip to content

Convert READMEs to markdown#3816

Open
slevis-lmwg wants to merge 31 commits intoESCOMP:b4b-devfrom
slevis-lmwg:readmes_to_md
Open

Convert READMEs to markdown#3816
slevis-lmwg wants to merge 31 commits intoESCOMP:b4b-devfrom
slevis-lmwg:readmes_to_md

Conversation

@slevis-lmwg
Copy link
Contributor

Description of changes

See title

Specific notes

Contributors other than yourself, if any:

CTSM Issues Fixed (include github issue #):
Fixes #2761

Are answers expected to change (and if so in what way)?
No

Any User Interface Changes (namelist or namelist defaults changes)?
No

Does this create a need to change or add documentation? Did you do so?
No

Testing performed, if any:
None needed

@slevis-lmwg slevis-lmwg self-assigned this Mar 16, 2026
@slevis-lmwg slevis-lmwg added documentation additions or edits to user-facing documentation or its infrastructure bfb bit-for-bit docs:update Significant update or fix needed to existing documentation docs-loc:other Relates to documentation somewhere not covered by the other docs-loc labels. labels Mar 16, 2026
@slevis-lmwg slevis-lmwg moved this to In Progress in CLM documentation Mar 16, 2026
@github-project-automation github-project-automation bot moved this to Ready to start (or start again) in CTSM: Upcoming tags Mar 16, 2026
@slevis-lmwg slevis-lmwg moved this from Ready to start (or start again) to In progress - b4b-dev in CTSM: Upcoming tags Mar 16, 2026
See if this renders better.
@slevis-lmwg
Copy link
Contributor Author

Note to self: Look for more READMEs that need conversion.

@ekluzek how should we handle the presence of both a README and a README.md in the /ctsm directory?

@ekluzek
Copy link
Collaborator

ekluzek commented Mar 16, 2026

@ekluzek how should we handle the presence of both a README and a README.md in the /ctsm directory?

@slevis-lmwg

Good question. The README.md shows up as what you see on github. And it's probably something we want to be short, with the main content being what we want people to see when they got to CTSM on github. In contrast, the content of the README details about how to use CTSM and some practical details about how to get around in the checkout.

So you could add the content of the plain README to the README.md, but make it at the end. The other option would be to have a file with a different name maybe something like: README_on_CTSM.md? Which sounds better to you?

@slevis-lmwg
Copy link
Contributor Author

slevis-lmwg commented Mar 18, 2026

There are several READMEs to address in cime_config/testdefs/testmods_dirs/clm/* and cime_config/usermods_dirs/clm/*/*that seem lower priority to me.

Next one to work on: python/ctsm/test

UPDATE on the above from a meeting with Erik earlier this afternoon:
We agreed that we do not need to replace the aforementioned "lower priority" READMEs with .md versions of them.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ekluzek it occurred to me that maybe I shouldn't be changing .rst files to .md, such as this one (already did it) and README.python_pkgs.rst (I will wait to hear back from you).

Copy link
Contributor Author

@slevis-lmwg slevis-lmwg Mar 19, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have started answering my own question. Changing the second of these files caused an error in a github workflow. I will see if changing the first file is a problem, too.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was confusing myself:

  • The original question still holds, whether it's ok the change README_GITFLEXMOD and README.python_pkgs from .rst to .md
  • I had to revert a different file from .md to no suffix (plain text) to correct a failing github workflow:
    README.unit_testing

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This note is related, but it's a reminder to myself:
If we keep README_GITFLEXIMOD.md, I now see additional formatting corrections that I would try.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would strongly prefer we convert reStructuredText files to Markdown, which is much more human-readable. Having just one markup format would also simplify doc viewing, as users would only need one rendering tool.

@slevis-lmwg
Copy link
Contributor Author

@samsrabin I will send you a review request:

  • Relatively simple PR, though you may choose to view each file whole to confirm that we still have readable files.
  • I posed a question for Erik that you may have insight into (see unresolved conversation above).

@slevis-lmwg slevis-lmwg requested a review from samsrabin March 19, 2026 23:50
@slevis-lmwg slevis-lmwg moved this from In Progress to In review in CLM documentation Mar 19, 2026
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I reversed this replacement with a later commit, but now I see that maybe I just needed to update the following:

.github/workflows/docs-build-and-deploy.yml:      - 'src/README.unit_testing'
.github/workflows/docs.yml:      - 'src/README.unit_testing'
.github/workflows/docs.yml:      - 'src/README.unit_testing'
doc/source/users_guide/testing/testing.rst:.. include:: ../../../../src/README.unit_testing

Similarly should I update these (for a file already in .md format):

.github/workflows/docs-build-and-deploy.yml:      - 'tools/README'
.github/workflows/docs.yml:      - 'tools/README'
.github/workflows/docs.yml:      - 'tools/README'

Copy link
Member

@samsrabin samsrabin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great start, Sam, thanks! I've requested some changes and added other comments.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This file at least appears to be valid Markdown, but it doesn't take advantage of any Markdown features. That's probably acceptable; mark this comment as resolved if you agree.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would be better to use the simpler Markdown syntax for section headings, using #, rather than this underlining method.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The headings could be changed to use Markdown heading syntax (prefix with #, ##), but I don't feel too strongly here.

@@ -2,32 +2,41 @@ mesh_mask_modifier is a tool that modifies mesh_mask files. It reads a
mesh_mask file and outputs a modified copy of the same file.

Files involved
--------------
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"Files involved" should be restored to be a heading.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would be better to use the simpler Markdown syntax for section headings, using #, rather than this underlining method. However, since the underlining method was already used, it's probably not worth the effort.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The bulleted lists should not be escaped, and each list item should be all on one line.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would strongly prefer we convert reStructuredText files to Markdown, which is much more human-readable. Having just one markup format would also simplify doc viewing, as users would only need one rendering tool.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Many strange artifacts left over from the conversion from reStructuredText to Markdown, as you can see by clicking the ellipsis > View File. See #3148 for instructions on using pandoc to convert automatically.

bin/git-fleximod -- Script to manage the needed sub-component source directories (handled with git submodule)
py_env_create ----- Script to setup the python environment for CTSM python tools using conda
python ------------ Python modules used in tools and testing and automated checking of ALL CTSM python scripts
doc --------------- Documentation of CTSM
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why the deleted periods and added whitespace here and elsewhere?

@github-project-automation github-project-automation bot moved this from In progress - b4b-dev to Stalled (needs review, blocked etc.) in CTSM: Upcoming tags Mar 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bfb bit-for-bit docs:update Significant update or fix needed to existing documentation docs-loc:other Relates to documentation somewhere not covered by the other docs-loc labels. documentation additions or edits to user-facing documentation or its infrastructure

Projects

Status: In review
Status: Stalled (needs review, blocked etc.)
Status: In Progress

Development

Successfully merging this pull request may close these issues.

3 participants